File Migration - Known issues

This topic summarizes the known issues that are related to file migration.

Table 1. Known issues
Issue Description Resolution
Error: The 'computerNameType' in eNAS SMB configuration contains an underscore (_). "message": "cvc-pattern-valid: Value 'XX_X' is not facet-valid with respect to pattern '[a-zA-Z0-9\\-]+' for type 'computerNameType'." There is a restriction that is imposed by PowerMax FILE regarding the use of underscores (_) in the computer name. Therefore, the user should remove the underscore from the computer name.
Error: The process of rediscovering the source NAS server is experiencing a longer-than-expected duration. To enhance the communication performance between SDNAS and eNAS/VNX CS, it is recommended to implement SSH lookup avoidance. This approach helps in minimizing the reliance on SSH lookups, thus improving the overall performance of the communication. To enhance the communication performance between SDNAS and eNAS/VNX CS, it is recommended to implement SSH lookup avoidance. This approach helps in minimizing the reliance on SSH lookups, thus improving the overall performance of the communication. 
cd /etc/ssh
vi sshd_config
Uncomment usedns and make it no, and then 
- /sbin/service sshd restart
Error: IMPORT_SESSION_ERROR_DURING_INITIAL_PROVISIONING_FAILED_TO_QUERY_FS_QUOTA_DETAILS Resume Import session failed with error - Parser 'parseFsTreeAndUserQuotas' has failed to parse the output of the management command. Configure user quotas on the specific filesystem or on all the filesystems that are involved in the migration, unable to generate the User Quota Report for the filesystem. Check the health status of the source system and the validity of the source quota configuration. Use Resume action to retry initial provisioning and continue the import process. The import process can be cancelled at any moment using Cancel action.
Import Sessions cannot be deleted manually. The session cannot be deleted. It cannot be deleted even if the session is cancelled or completed.
Warning: NEW_SESSION_PRECHECK_TARGET_FILESYSTEM_SIZE_DIFFERENT_FROM_SOURCE_FILESYSTEM_SIZE" NEW_SESSION_PRECHECK_TARGET_FILESYSTEM_SIZE_DIFFERENT_FROM_SOURCE_FILESYSTEM_SIZE" The recommended target FS size, which is used for imported filesystems on SDNAS (unless overridden by the user when creating an import session) is calculated considering many factors.
  1. File level deduplication/compression is not supported by SDNAS;
  2. UFS32 -> UFS64 metadata overhead
  3. SDNAS LUN data
  4. FS-full threshold of 500 Mb
  5. IMT internal data, including per inode records;
  6. Other potential overheads
Error: NEW_SESSION_PRECHECK_PARAM_MISMATCH_NFS_TRANS_CHECKSUM 
{"id":13166520130,"name": 
"NEW_SESSION_PRECHECK_PARAM_
MISMATCH_NFS_TRANS_CHECKSUM",
"severity":3,
"briefDescription":
"Cannot create an import session because the 
value of the parameter 'nfs.transChecksum' 
on the source NAS server differs from the 
value on the target system. 
				
","fullDescription":"Cannot create 
an import session over import connection 'XXX'. 
The value of the parameter 'nfs.transChecksum' 
on source NAS server 'XX 'is '1'.
The failure occurred because it differs from the value on the target system (value='0'). This parameter defines whether to compute NFS Request Checksum. The value of this parameter must be the same on the source system and on the target system.","recommendedAction":"Ensure that the value of this parameter on the source NAS server is identical to the corresponding value on the target system." 		Run this command on eNAS server_param ALL -facility nfs -modify transChecksum -value 0.
Error: Import state shows as Error in GUI post cutover sometimes. In the UI, it would be an error for a certain period. There is no specific error or warning that is provided for this error. CCMD- FS_IMPORT_COPYING_INCREMENTAL is posted for every cutover operation to inform the administrator that the process may take some time. After the cutover, the administrator should refresh the UI page to retrieve the latest session status. CmdSDNASCLImportSessionDataManagementCmd::startresumeMigrationSessionDone:1807: Import info event CCMD FS_IMPORT_COPYING_INCREMENTAL: The import of the file system 'XX' is fetching the differences from the baseline data that was imported during the initial copy. Data access requests reach the file system on the target NAS server, and all changes are mirrored back to the source NAS server. As a result, clients may experience performance degradation and are still dependent on the source availability. The process may take a while, depending on the content of the source file system. Import session 'XX' is reporting the progress and the estimated remaining time for the import process.
Issue: SMB event Notification enabled on file system after Migration without configuring SMB server on NAS server In the V3 system, the SMB server was not configured. However, after migrating to V4 PowerMax, SMB event notifications are enabled by default for all file systems. The NAS server only has an NFS server configured and does not have the SMB server set up. On the V4 platform, if the SMB server is not enabled, there is no available option to enable it. In case the user want to disable the SMB event Notifications, configure the SMB Server on the NAS Server, and then disable it.
Issue: NTP Drift- The time difference (delta) between the source and destination Symmetrix should be less than 5 seconds. The session is in a "Non_Ready" state and cannot be imported. Run date on File (V4) guest 
In FILE-1, the current date is 
"Mon Jul 17 09:07:57 UTC 2023."
Now, on V3 run the following command: 
server_date ALL yymmddhhmm
For example, to set the server date to "23 07 17 09 08" (2023 year, 07 month, 17 day, 09 hours, and 08 minutes), use the command: 
o3 
				server_date ALL 230717090807170908
This setting adjusts the date of the server and time to the specified values. 
 FILE-1:~ # date Mon Jul 17 09:07:57 UTC 2023
Now on the V3 run 
server_date ALL yymmddhhmm
For example: 23 07 17 09 08 (2023 year 07 Month, 17 Day, 09 hours 08 minutes) 
server_date ALL 2307170908
Issue: By default, migration alerts are disabled on V4 PowerMax UI. Alerts that are related to import sessions do not appear on the Alerts page if the corresponding policies are not enabled. Also, the alerts that are associated with the health status on the import session page also remain invisible. Go to Settings-> Alerts-> Alert Policies- > Enable Migration Session and Migration FS policies.